Systems, methods, and apparatuses for implementing persistent management agent (pma) functions for the control and coordination of dpu and dslam components

ABSTRACT

In accordance with embodiments disclosed herein, an exemplary system or computer implemented method for implementing Persistent Management Agent (PMA) functions for the control and coordination of DPU and DSLAM components may include, for example: a memory to store instructions for execution; one or more processors to execute the instructions; a virtualized module operating on virtualized computing infrastructure, in which the virtualized module is to provide a virtualized implementation of a plurality of functions associated with one or more remotely located Distribution Point Units (DPUs) and/or Digital Subscriber Line Access Multiplexers (DSLAMs), each of the one or more remotely located DPUs and/or DSLAMs having a plurality of broadband lines coupled thereto; in which the virtualized module is to further control Persistent Management Agent (PMA) functions and control coordination of the one or more remotely located DPUs and/or DSLAMs and the plurality of broadband lines coupled with the one or more remotely located DPUs and/or DSLAMs by virtualizing one or more functions of the one or more remotely located DPUs and/or DSLAMs to operate on the virtualized computing infrastructure; and a network interface to receive data and send control instructions for operation of the plurality of broadband lines to and from the one or more remotely located DPUs and/or DSLAMs. Other related embodiments are disclosed.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

TECHNICAL FIELD

The subject matter described herein relates generally to the fields ofcomputing and digital communications, and more particularly, to systems,methods, and apparatuses for implementing the virtualization of accessnode functions as well as the systems, methods, and apparatuses forimplementing Persistent Management Agent (PMA) functions for the controland coordination of DPU and DSLAM components.

BACKGROUND

The subject matter discussed in the background section should not beassumed to be prior art merely as a result of its mention in thebackground section. Similarly, a problem mentioned in the backgroundsection or associated with the subject matter of the background sectionshould not be assumed to have been previously recognized in the priorart. The subject matter in the background section merely representsdifferent approaches, which in and of themselves may also correspond toembodiments of the claimed subject matter.

In the networking arts the computational burdens set upon remotelydeployed network components, (e.g., such as Distribution Point Units(DPUs) and Digital Subscriber Line Access Multiplexers (DSLAMs) deployedinto the field) are increasing, requiring these network components totake on increased roles, while at the same time, the physical size ofthese units have been trending toward becoming smaller. Although thesize of such network components are trending smaller, the physical spaceavailable within cabinets which hold such components may nevertheless beconstrained. Further still, remote cooling capacity and electricalrequirements are sometimes constrained and are universally more costlythan equivalent power consumption at a well designed data center.

Unlike specialized network components conventionally deployed into thefield, data centers leverage low-cost commoditized hardware toinstantiate many virtual machines enabling a significantly lower costper computation at each such virtual machine, below that of dedicatedcomputers, and far below that of dedicated computational hardware andcircuitry of network-located equipment.

As network components become smaller and are deployed further into thesupporting network they become increasingly expensive, increasinglycomplex, and increasingly difficult to manage. Powering such devices maybe limited or intermittent, for instance, as commonly happens whenreverse powering such devices via power provided from the CPE isinterrupted, as some CPE devices may be turned off and thus, cease theflow of power to the supported network component.

The Access Node (also referred to as “AN”) is the first aggregationpoint in the access network. An Access Node may itself be any of aDSLAM, a DPU, an OLT (“Optical Line Termination” unit), a CMTS (“CableModem Termination System”), an Ethernet aggregation switch, etc. Asbroadband speeds increase, the increased speeds mandate the deployment,support, and utilization of ever advanced signal processing andscheduling capabilities for access nodes, all of which increasescomputation and storage requirements at the remotely deployed networkcomponents, which in turn squeezes the computational capabilities andcomputing resources available at the access nodes. At the same time datacenters and the cloud have ever increasing computational and storagecapabilities at decreasing costs using commodity hardware. New methodsto virtualize the functions in the access node and leverage virtualizedcomputing resources are now becoming useful.

Centralization of certain remotely deployed network components may helpto alleviate some of the constraints and computational burdens placedupon such field components, however, the entities conventionallyresponsible for manufacturing such components have yet to provide anyworkable solutions.

The present state of the art may therefore benefit from systems,methods, and apparatuses for implementing the virtualization of accessnode functions as well as the systems, methods, and apparatuses forimplementing Persistent Management Agent (PMA) functions for the controland coordination of DPU and DSLAM components as described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are illustrated by way of example, and not by way oflimitation, and will be more fully understood with reference to thefollowing detailed description when considered in connection with thefigures in which:

FIG. 1 illustrates an exemplary architecture in which embodiments mayoperate;

FIG. 2 depicts another exemplary architecture in accordance withdescribed embodiments;

FIG. 3 depicts an alternative exemplary architecture in accordance withdescribed embodiments;

FIG. 4 depicts an alternative exemplary architecture in accordance withdescribed embodiments;

FIG. 5 depicts an alternative exemplary architecture in accordance withdescribed embodiments;

FIG. 6 depicts an alternative exemplary architecture in accordance withdescribed embodiments;

FIG. 7 depicts a flow diagram of a method for implementing a VANFalgorithm for traffic, power, and vectoring management;

FIG. 8 depicts an alternative exemplary architecture in accordance withdescribed embodiments;

FIG. 9 illustrates a diagrammatic representation of a system inaccordance with which embodiments may operate, be installed, integrated,or configured;

FIG. 10 depicts a flow diagram of a method for implementing thevirtualization of access node functions;

FIG. 11 illustrates a diagrammatic representation of a system inaccordance with which embodiments may operate, be installed, integrated,or configured;

FIG. 12 depicts a flow diagram of a method for implementing PersistentManagement Agent (PMA) functions for the control and coordination of DPUand DSLAM components; and

FIG. 13 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system.

DETAILED DESCRIPTION

Described herein are apparatuses, systems and methods for implementingthe virtualization of access node functions as well as the systems,methods, and apparatuses for implementing Persistent Management Agent(PMA) functions for the control and coordination of DPU and DSLAMcomponents.

In accordance with one embodiment, an exemplary system or computerimplemented method for implementing the virtualization of access nodefunctions may include, for example: a memory to store instructions forexecution; one or more processors to execute the instructions; a controlplane interface to communicably interface the system with an access nodeover a network, in which the access node is physically coupled with aplurality of broadband lines; a virtualized module to provide avirtualized implementation of a plurality of functions of the accessnode at the system, in which the virtualized module executes on avirtualized computing infrastructure; the control plane interface of thesystem to receive current operational data and current operatingconditions for the plurality of broadband lines from the access node;the virtualized module to update the virtualized implementation of theplurality of functions of the access node at the system according to thecurrent operational data and the current operating conditions receivedfrom the access node; an analysis module to analyze the currentoperational data and the current operating conditions received from theaccess node; an instruction module to generate control parameters toaffect operation of the access node based on the analysis of the currentoperational data and the current operating conditions received; and thecontrol plane interface to send the control parameters to the accessnode for adoption at the access node.

In accordance with a different embodiment, an exemplary system orcomputer implemented method for implementing Persistent Management Agent(PMA) functions for the control and coordination of DPU and DSLAMcomponents may include, for example: a memory to store instructions forexecution; one or more processors to execute the instructions; avirtualized module operating on virtualized computing infrastructure, inwhich the virtualized module is to provide a virtualized implementationof a plurality of functions associated with one or more remotely locatedDistribution Point Units (DPUs) and/or Digital Subscriber Line AccessMultiplexers (DSLAMs), each of the one or more remotely located DPUsand/or DSLAMs having a plurality of broadband lines coupled thereto; inwhich the virtualized module is to further control Persistent ManagementAgent (PMA) functions and control coordination of the one or moreremotely located DPUs and/or DSLAMs and the plurality of broadband linescoupled with the one or more remotely located DPUs and/or DSLAMs byvirtualizing one or more functions of the one or more remotely locatedDPUs and/or DSLAMs to operate on the virtualized computinginfrastructure; and a network interface to receive data and send controlinstructions for operation of the plurality of broadband lines to andfrom the one or more remotely located DPUs and/or DSLAMs.

Such means enable the virtualization and centralization of functionalitydeployed at remote network components into more cost efficient andmaintenance friendly environments, such as purpose built data centers.Many functions which are conventionally implemented and carried out bythe remotely deployed network components do not necessarily requirespecialized hardware, and as such, may be abstracted from the physicaldevices via virtualization efforts. However, conventional solutions todate have failed to enable such efforts.

For instance, implementation of VDSL (“Very-high-bit-rate DigitalSubscriber Line”) technologies requires specialized chipsets; however,such chip manufacturers simply do not provide direct support for theabstraction and virtualization of remotely deployed VDSL capabilities.Within a VDSL capable DSLAM there is required a dedicated processorwhich draws expensive remote power provided into field deployments, suchas network equipment cabinets, etc. Conversely, offloading variousfunctions from the remotely deployed equipment for processing at anotherpurpose build location, such as a data center, provides computationalefficiencies, enables access to lower cost electricity and cooling, andmay serve to simplify maintenance, upgrades, management, andre-configuration through the economies of scale and centralizationinherent to such data centers, versus the many distributed fieldlocations into which the network elements are deployed.

For instance, consider a data center with thousands of racks, eachhaving a dozen rack-mountable units, each with a dozen blade typeservers, each blade server having a dozen processors, and each processorhaving, for example, 16 distinct processing cores, with each processingcore capable to support differing virtualized functions or VirtualizedMachines (VMs). Such an environment certainly is not without costsincluding capital cost, cooling costs, electricity costs, and the costto provide the physical space to house such computational means.However, scaling up such a hardware environment in a centralizedlocation is significantly less expensive to operate on a per virtualmachine basis than deploying compute infrastructure in multiple fieldlocations, power for such a hardware environment is less expensive andcan be selected for cost-efficiency as well as for access toenvironmentally friendly power, and maintenance is additionallysimplified as it is much easier to facilitate operations of 1000's ofvirtual machines residing upon hardware in a single physical locationthan having to send maintenance technicians literally to thousands ofdeployed field locations across a large geographic region.

Virtualizing network functions makes them readily accessible andrelatively easy to upgrade and manage. Virtual network functions can bere-configured and chained together to create new capabilities and newservices in increasingly flexible ways that encourage innovation andimprove an end-customer's user experience. However, with the exceptionof back-office and OSS/BSS functionality, such network functions forbroadband Internet access have always been performed inside NetworkElements (NEs) as it has been thought, incorrectly, that suchcapabilities cannot be abstracted from the relevant network devices,access nodes, or whatever network components are responsible for theirnative support and execution.

Access node virtualization in such a broadband networking environmentmay thus benefit from, among others, savings from using low-cost computeinfrastructure in place of expensive computing within the networkelements; software upgrades instead of hardware replacements;utilization of Virtual Machines (VMs) that are easily portable andeasily backed-up versus physical remotely deployed networkingcomponents; rapid and flexible lifecycle management processes; fasterorder delivery, faster recovery, auto-scaling of capacity to demand,etc.; unified touch-point to simplify management; enablement ofinfrastructure-sharing; encouragement of services innovation; easiercreation of new functions and changes made to change existing functions;utilization of “service chaining” to build up higher-level services fromlower-level building blocks; and improved performance and QoE (Qualityof Experience) for service subscribers, broadband network operators,broadband technicians, and broadband customers and end-users.

Abstracting many of the functions from remotely deployed networkcomponents and virtualizing them onto processing cores and computationalhardware in centralized environments or Points of Presence (PoPs) may beaccomplished without requiring the specialized chipsets associated withsuch remote equipment as many such functions that are conventionallyimplemented by such remote equipment does not necessarily require thespecialized circuitry. For instance, the core of an Internet Protocol(IP) router requires dedicated hardware for a subset of its functions,if those functions are to be carried out quickly and efficiently,however, other functions do not require the specialized circuitry andmay be carried out via a server within software at any location,regardless of the physical location of the native device. Additionally,virtualizing such functions within software further enables significantflexibility for upgrades, changes, and maintenance, and these may beconducted in a centralized location. The infrastructure for suchfunctionality may thus be implemented by a cloud services provider as aservice to other entities, for instance, where a first entity providesthe hardware, infrastructure, and relevant computational functionalityand access regime through which to access the virtualized functions andthen a second entity subscribes or purchases such services from thefirst, resulting in a mutually beneficial business relationship.

Such a cloud services provider may therefore enable and provide as aservice to other entities the infrastructure to support certain NetworkService Virtualization (NSV) and/or Software-Defined Access Networks(SDAN) offerings, with the software that performs the functions providedby vendors or operators, and operated by operators. Alternatively, otherentities may create the software that performs the functions, oroperators may perform NSV and/or SDAN offerings internally on their ownhardware within their own data centers.

Access nodes used for Fiber to the distribution point (FTTdp), alsoknown as DPUs or DSLAMs, may be well suited for such virtualizationefforts. This is because these access nodes are becoming physicallysmaller and are being integrated deeper into the network, while at thesame time, speeds are increasing and the ANs themselves are handlingincreasingly complex signal processing which helps to enable the fasterbroadband connectivity speeds, further, such access nodes are performingadditional signal processing locally and operate faster in terms ofserving the total bandwidth moving through such devices, all of whichexacerbates the problematic demands on computational capabilities ofsuch devices. It is therefore necessary to either to have very expensiveprocessors locally within such access nodes to suitably perform suchfunctionality, or the functionality may be performed remotely byvirtualized machines supported by appropriate hardware capabilities,where such functions may be abstracted from the remotely deployeddevices and operated on such bare-metal servers or VMs in a differentphysical location.

Network Functions Virtualization (NFV) is moving the compute processinginvolved with network functions from such dedicated servers, DSLAMs,DPUs, Access Nodes, and other such network devices into the cloud, assupported by data centers or other Point of Presence (PoP)implementations of computing infrastructure. When it comes to broadbandaccess functions, virtualization is being actively investigated fornetwork components such as the Broadband Network Gateway (BNG)/BroadbandRemote Access Server (BRAS), and for the Customer Premises Network(CPE)/Residential Gateway (RG).

The methodologies described herein provide means by which to virtualizesuch functions, and in particular, functions associated with the AccessNode (AN) (e.g., be it a DSLAM, DPU, OLT, CMTS, or Ethernet aggregationswitch) as what may be called Virtualized Access Node Functions (VANFs).Such systems, methods, and apparatuses for implementing thevirtualization of access node functions as well as the systems, methods,and apparatuses for implementing Persistent Management Agent (PMA)functions for the control and coordination of DPU and DSLAM componentshave yet to date be considered or addressed in the conventional artsbecause either they are new or because others have simply assumed thatsuch functions must be located within the remotely deployed access nodeitself. The means described herein thus take a somewhat contrarian viewby abstracting such functions from the ANs deployed into the field andenabling the virtualization and use of such functions at a differentlocation.

Many broadband access network control and management functions currentlyperformed in the access node are nevertheless suitable to virtualizationand remote execution from their native equipment (e.g., running suchfunctions at a data center rather than at a field deployed AN). Thereare likewise many new network functions that may either be performed inan access node locally or be performed via the Virtualized Access NodeFunctions (VANFs) described herein.

The embodiments described herein specifically provide means andmethodologies by which to virtualize specific network functions that areconventionally performed locally at a broadband access node deployedremotely in the field.

In the following description, numerous specific details are set forthsuch as examples of specific systems, languages, components, etc., inorder to provide a thorough understanding of the various embodiments. Itwill be apparent, however, to one skilled in the art that these specificdetails need not be employed to practice the disclosed embodiments. Inother instances, well known materials or methods have not been describedin detail in order to avoid unnecessarily obscuring the disclosedembodiments.

In addition to various hardware components depicted in the figures anddescribed herein, embodiments further include various operations whichare described below. The operations described in accordance with suchembodiments may be performed by hardware components or may be embodiedin machine-executable instructions, which may be used to cause ageneral-purpose or special-purpose processor programmed with theinstructions to perform the operations. Alternatively, the operationsmay be performed by a combination of hardware and software, includingsoftware instructions that perform the operations described herein viamemory and one or more processors of a computing platform.

Embodiments also relate to a system or apparatus for performing theoperations herein. The disclosed system or apparatus may be speciallyconstructed for the required purposes, or it may comprise a generalpurpose computer selectively activated or reconfigured by a computerprogram stored in the computer. Such a computer program may be stored ina non-transitory computer readable storage medium, such as, but notlimited to, any type of disk including floppy disks, optical disks,flash, NAND, solid state drives (SSDs), CD-ROMs, and magnetic-opticaldisks, read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic or optical cards, or any type of media suitable forstoring non-transitory electronic instructions, each coupled to acomputer system bus. In one embodiment, a non-transitory computerreadable storage medium having instructions stored thereon, causes oneor more processors within an apparatus to perform the methods andoperations which are described herein. In another embodiment, theinstructions to perform such methods and operations are stored upon anon-transitory computer readable medium for later execution.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus nor are embodimentsdescribed with reference to any particular programming language. It willbe appreciated that a variety of programming languages may be used toimplement the teachings of the embodiments as described herein.

FIG. 1 illustrates an exemplary architecture 100 in which embodimentsmay operate. Asymmetric Digital Subscriber Line (ADSL) systems (one formof Digital Subscriber Line (DSL) systems), which may or may not includesplitters, operate in compliance with the various applicable standardssuch as ADSL1 (G.992.1), ADSL-Lite (G.992.2), ADSL2 (G.992.3),ADSL2-Lite G.992.4, ADSL2+(G.992.5) and the G.993.x emergingVery-high-speed Digital Subscriber Line or Very-high-bitrate DigitalSubscriber Line (VDSL) standards, as well as the G.991.1 and G.991.2Single-Pair High-speed Digital Subscriber Line (SHDSL) standards, allwith and without bonding, and/or the G.997.1 standard (also known asG.ploam).

In accordance with embodiments described herein, end-user consumers,including residential consumers and business consumers, may connect tothe Internet by way of a Wide Area Network (WAN) backhaul connection toa Service Provider (SP), such as an Internet Service Provider (ISP), orto a Service Provider that provides one or more of data connectivity,voice connectivity, video connectivity, and mobile device connectivityto a plurality of subscribers. Such Service Providers may include aDigital Subscriber Line (DSL) internet service provider which providesits subscribing end-users with Internet bandwidth at least partiallyover copper twisted pair telephone lines, such as that conventionallyutilized to carry analog telephone service (e.g., Plain Old TelephoneService (POTS); a coaxial cable internet service provider which providesend-users with Internet bandwidth at least partially over coaxial cable,such as that conventionally utilized to carry “cable” televisionsignals; or a fiber optics internet service provider which providesend-users with Internet bandwidth at over fiber optic cable thatterminates at a customer's premises. Other variants exist as well, suchas ISPs which provide Internet bandwidth as an analog signal over ananalog telephone based connection, ISPs that provide Internet bandwidthover a one-way or two-way satellite connection, and ISPs that provideInternet bandwidth at least partially over power lines, such as powerlines conventionally utilized to transmit utility power (e.g.,electricity) to an end-user's premises, or ISPs that provide Internetbandwidth at least partially over wireless channels, such as wireless(e.g., WiFi) connectivity at hotspots, or mobile data connectivity viatechnologies and standards such as WiMax, 3G/4G, LTE, etc.

In performing the disclosed functions, systems may utilize a variety ofoperational data (which includes performance data) that is available atan Access Node (AN).

In FIG. 1, user's terminal equipment 102 (e.g., a Customer PremisesEquipment (CPE) device or a remote terminal device, network node, LANdevice, etc.) is coupled to a home network 104, which in turn is coupledto a Network Termination (NT) Unit 108. DSL Transceiver Units (TU) arefurther depicted (e.g., a device that provides modulation on a DSL loopor line). In one embodiment, NT unit 108 includes a TU-R (TU Remote),122 (for example, a transceiver defined by one of the ADSL or VDSLstandards) or any other suitable network termination modem, transceiveror other communication unit. NT unit 108 also includes a ManagementEntity (ME) 124. Management Entity 124 can be any suitable hardwaredevice, such as a microprocessor, microcontroller, or circuit statemachine in firmware or hardware, capable of performing as required byany applicable standards and/or other criteria. Management Entity 124collects and stores, among other things, operational data in itsManagement Information Base (MIB), which is a database of informationmaintained by each ME capable of being accessed via network managementprotocols such as Simple Network Management Protocol (SNMP), anadministration protocol used to gather information from a network deviceto provide to an administrator console/program or via TransactionLanguage 1 (TL1) commands, TL1 being a long-established command languageused to program responses and commands between telecommunication networkelements, or using YANG data models via Network Configuration Protocol(NETCONF), which is a newer language initially defined forsoftware-defined networking and virtualization.

Each TU-R 122 in a system may be coupled with a TU-C (TU Central) in aCentral Office (CO) or other central location. TU-C 142 is located at anAccess Node (AN) 114 in Central Office 146. A Management Entity 144likewise maintains an MIB of operational data pertaining to TU-C 142.The Access Node 114 may be coupled to a broadband network 106 or othernetwork, as will be appreciated by those skilled in the art. TU-R 122and TU-C 142 are coupled together by a loop 112, which in the case ofVDSL may be a twisted pair line, such as a telephone line, which maycarry other communication services besides DSL based communications.

Several of the interfaces shown in FIG. 1 are used for determining andcollecting operational data. The Q interface 126 provides the interfacebetween the Network Management System (NMS) 116 of the operator and ME144 in Access Node 114. Parameters specified in the G.997.1 standardapply at the Q interface 126. The near-end parameters supported inManagement Entity 144 may be derived from TU-C 142, while far-endparameters from TU-R 122 may be derived by either of two interfaces overthe UA interface. Indicator bits and EOC messages may be sent usingembedded channel 132 and provided at the Physical Medium Dependent (PMD)layer, and may be used to generate the required TU-R 122 parameters inME 144. Alternately, the Operations, Administration and Maintenance(OAM) channel and a suitable protocol may be used to retrieve theparameters from TU-R 122 when requested by Management Entity 144.Similarly, the far-end parameters from TU-C 142 may be derived by eitherof two interfaces over the U-interface. Indicator bits and EOC messagesprovided at the PMD layer may be used to generate the required TU-C 142parameters in Management Entity 124 of NT unit 108. Alternately, the OAMchannel and a suitable protocol may be used to retrieve the parametersfrom TU-C 142 when requested by Management Entity 124.

At the U interface (also referred to as loop 112), there are twomanagement interfaces, one at TU-C 142 (the U-C interface 157) and oneat TU-R 122 (the U-R interface 158). U-C Interface 157 provides TU-Cnear-end parameters for TU-R 122 to retrieve over the U interface/loop112. Similarly, U-R interface 158 provides TU-R near-end parameters forTU-C 142 to retrieve over the U interface/loop 112. The parameters thatapply may be dependent upon the transceiver standard being used (forexample, G.992.1 or G.992.2). The G.997.1 standard specifies an optionalOperation, Administration, and Maintenance (OAM) communication channelacross the U interface. If this channel is implemented, TU-C and TU-Rpairs may use it for transporting physical layer OAM messages. Thus, theTU transceivers 122 and 142 of such a system share various operationaldata maintained in their respective MIBs. Interfaces V 156 and V-C 159are further depicted within the CO 146 at different points of the loop112. Interface G at element 169 is connected between the home network104 and the Network Termination unit 108

Depicted within FIG. 1 are system(s) 170, for instance, which host orprovide a VANF Implementation, and such system(s) 170 may reside at anyof multiple optional locations. Moreover, system(s) 170 may constitute asingle large system having therein a large collection of computingequipment to implement the methodologies described herein or constitutemultiple related and communicably interfaced systems or sub-systems tocarry out the described embodiments. In certain embodiments, system(s)170 embody a data center or reside within a data center which operate ina physical geographic location which is remote and distinct from thenetwork components, access nodes, DSLAMs, DPUs, OLTs, and other suchNetwork Equipment for which functions are abstracted and virtualizedelsewhere. According to the depicted embodiment at FIG. 1, the system(s)170 are shown to operate at various optional locations in accordancewith several alternative embodiments. For example, in accordance withone embodiment, system(s) 170 are communicably interfaced throughbroadband network 106, for instance, through a public Internet, VPN, orother network utilized to reach DSL networking equipment. For instance,system(s) 170 need not be co-located with the DSL network equipment inorder to provide abstraction and virtualization of network elementfunctions as well as associated services, and to be sure, such system(s)170 most often will not be co-located with the network elements andother network components for which the functions are abstracted andvirtualized. Such system(s) 170 may therefore operate within the“cloud,” for instance, at a remote hosted computing facility or datacenter within which the system(s) 170 reside, from which such system(s)170 are connected over potentially long distances via appropriatenetworking technology to the remotely deployed network equipment. Such acloud service provider may therefore provide the abstracted andvirtualized functions to another entity via the “cloud” as a service fora subscription fee. Or the cloud service provider can provide thecomputing infrastructure that the functions run on. Such services may beprovided to broadband network providers, DSL network operators, DSLnetwork services providers, etc. In alternative embodiments, it isfeasible for the system(s) 170 to operate within the Central Office 146and be communicably interfaced through NMS 116 or system(s) 170 mayoperate outside of the Central Office 146 and be communicably interfacedeither to NT unit 108 or interfaced into the TU-R 122 within NT unit108.

As used herein, the terms “user,” “subscriber,” and/or “customer” referto a person, business and/or organization to which communicationservices and/or equipment are and/or may potentially be provided by anyof a variety of service provider(s). Further, the term “customerpremises” refers to the location to which communication services arebeing provided by a service provider. For example, Public SwitchedTelephone Network (PSTN) used to provide DSL services to customerpremises are located at, near and/or are associated with the networktermination (NT) side of the telephone lines. Example customer premisesinclude a residence or an office building.

As used herein, the term “service provider” refers to any of a varietyof entities that provide, sell, provision, troubleshoot and/or maintaincommunication services and/or communication equipment. Example serviceproviders include a telephone operating company, a cable operatingcompany, a wireless operating company, an internet service provider, orany service that may independently or in conjunction with a broadbandcommunications service provider offer services that diagnose or improvebroadband communications services (DSL, DSL services, cable, etc.).

Additionally, as used herein, the term “DSL” refers to any of a varietyand/or variant of DSL technology such as, for example, Asymmetric DSL(ADSL), High-speed DSL (HDSL), Symmetric DSL (SDSL), Veryhigh-speed/Very high-bit-rate DSL (VDSL) and/or Fast Access toSubscriber Terminals (G.fast). Such DSL technologies are commonlyimplemented in accordance with an applicable standard such as, forexample, the International Telecommunications Union (I.T.U.) standardG.992.1 (a.k.a. G.dmt) for ADSL modems, the I.T.U. standard G.992.3(a.k.a. G.dmt.bis, or G.adsl2) for ADSL2 modems, I.T.U. standard G.992.5(a.k.a. G.adsl2plus) for ADSL2+ modems, I.T.U. standard G.993.1 (a.k.a.G.vdsl) for VDSL modems, I.T.U. standard G.993.2 for VDSL2 modems,I.T.U. standard G.9701 for G.fast modems, I.T.U. standard G.994.1 (G.hs)for modems implementing handshake, and/or the I.T.U. G.997.1 (a.k.a.G.ploam) standard for management of DSL modems.

References to connecting a DSL modem and/or a DSL communication serviceto a customer are made with respect to exemplary Digital Subscriber Line(DSL) equipment, DSL services, DSL systems and/or the use of ordinarytwisted-pair copper telephone lines for distribution of DSL services andit shall be understood that the disclosed methods and apparatus tocharacterize and/or test a transmission medium for communication systemsdisclosed herein may be applied to many other types and/or variety ofcommunication equipment, services, technologies and/or systems. Forexample, other types of systems include wireless distribution systems,wired or cable distribution systems, coaxial cable distribution systems,Ultra High Frequency (UHF)/Very High Frequency (VHF) radio frequencysystems, satellite or other extra-terrestrial systems, cellulardistribution systems, broadband power-line systems and/or fiber opticnetworks. Additionally, combinations of these devices, systems and/ornetworks may also be used. For example, a combination of twisted-pairand coaxial cable interfaced via a balun connector, or any otherphysical-channel-continuing combination such as an analog fiber tocopper connection with linear optical-to-electrical connection at anOptical Network Unit (ONU) may be used.

The phrases “coupled to,” “coupled with,” connected to,” “connectedwith” and the like are used herein to describe a connection between twoelements and/or components and are intended to mean coupled/connectedeither directly together, or indirectly, for example via one or moreintervening elements or via a wired/wireless connection. References to a“communication system” are intended, where applicable, to includereference to any other type of data transmission system.

FIG. 2 depicts another exemplary architecture 200 in accordance withdescribed embodiments including how VANFs may be performed onremotely-located compute infrastructure. More particularly, a simplifiedview of broadband access network elements (NEs) are depicted, beginningwith the Customer premises Equipment (CPE) components 250A, 250B, 250C,250D, 250E, and 250F at the bottom of FIG. 2 depicted as being connectedvia access lines 260 (e.g., wired or wireless access paths) through oneof the depicted residential gateways 245. The Residential Gateway (RG)network components depicted here may themselves be a type of CPEaccording to the various embodiments. The Residential gateways 245 areconnected to the access nodes 240A, 240B, and 240C which in turn connectthrough access node aggregation 225 devices such as Optical LineTerminals (OLTs) or Ethernet aggregation switches as is depicted witheach of Access Nodes 240A and 240B. Alternatively, or additionally asthe case may be, the access nodes may connect to other network(s) 205,such as the public Internet, VPNs, or to other private networks througha Broadband Network Gateway (BNG) 220 (sometimes also called a BroadbandRemote Access Server (BRAS)) via backhaul 230 as is depicted with accessnode 240C. Management systems and controller(s) 215 connect to thevarious Network Elements over any of a variety of connections includingvia a private backbone 210 as is depicted here.

In the most general sense, the methodologies described herein seek toabstract functions from the access nodes 240A-C, be they DSLAMs, DPUs,OLTs, CMTS devices, etc. For instance, according to particularembodiments, the management, systems, and controller(s) 215 (e.g., whichmay correspond to the “system(s)” as depicted at element 170 of FIG. 1),may serve as a virtualized computing hardware or infrastructure forfunctionality abstracted from the access nodes 240A-C, including anyfunction or functionality capable of abstraction from such networkelements and corresponding virtualization at the management, systems,and controller(s) 215.

In alternative embodiments, it may prove useful to abstract certainuseful access node functions, but not all functions possible ofabstraction and corresponding virtualization.

With regard to broadband networking, it may be preferential to abstractfunctions from the access nodes 240A-C that relate to scheduling andvectoring control as a foundation and then optionally abstract otherfunctions as the need arises for any particular implementation.

Notwithstanding the abstraction and virtualization of functions from theaccess nodes 240A-C, it is nevertheless mandatory to maintain physicalaccess nodes 240A-C in the field, such as DSLAMs, as it is the physicaldevices which terminate the broadband lines and provide networkconnectivity to the broadband lines, regardless of whether such linesare optical, DSL, cable, etc.

According to the depicted embodiment, the management systems andcontroller(s) 215 receives information from the access nodes 240A-C.Take vectoring for example. Computing vectoring coefficients at theremote machine must have error samples returned back from the accessnodes 240A-C which could be averages, or summary information, but mustbe error information about the broadband lines themselves. Vectoringcontrol at the management systems and controller(s) 215 would thencalculate the vectoring coefficients based on the error sample datareturned from the access nodes 240A-C and such vectoring coefficientswould then be returned back to the access nodes 240A-C which implementthe vectoring coefficients on the respective broadband lines.

With regard to scheduling, it may be necessary to know the queueoccupancy which may constitute data which resides within the transceiverfor the respective access node 240A-C which is connected with acorresponding broadband line. Alternatively, such information may beretrievable from a policy manager or a resource assignment system. Suchinformation could be forced to be returned or pulled from the accessnodes 240A-C or pulled through the access nodes 240A-C from the CPE, orthe information could be pulled directly from a network managementsystem. Scheduling information need not be real-time data, and as such,various aggregation and data access schemes are often acceptable. Theaccess nodes 240A-C may additionally pull real time operational dataregarding the broadband lines in which the management systems andcontroller(s) 215 will then tell what time slots are assigned on whatlines. For instance, line 1 may be identified as using particular timeslots, frames, downstream scheduling, upstream scheduling, etc.

FIG. 3 depicts an alternative exemplary architecture 300 in accordancewith described embodiments, and more particularly, depicts connectionsto the computational resources utilized for virtualization in accordancewith certain embodiments. CPEs 340 and access nodes 350 (e.g., DPU,DSLAM, OLT, CMTS; Located in a Central Office (CO), exchange, remoteterminal, cabinet, pedestal, terminal, head end, etc.) connect withvirtualized compute resources which are remotely located in the cloud,Point-of-presence (PoP), or data center 310 as depicted here.Specifically, the CPE 340 is connected via access line 335 to the accessnode 350 which is located in the central office (CO), an exchange, aremote terminal, a cabinet, a pedestal, a terminal, a head-end, etc.,which in turn is connected via a backhaul 330 to the access nodeaggregation 360 device, and then back to the cloud, PoP, or data center310. The dashed lines from CPE 340 to the cloud, PoP, or data center 310and from access node 350 back to the cloud, PoP data center 310represent logical connections 375.

For instance, a Virtual Network Function (VNF) 380 implemented via thecloud, PoP, or data center 310 may communicate with the access node 350via a control plane interface 385 which resides between the VirtualNetwork Function and the access node aggregation 360 device. Asdepicted, the access node 350 is coupled with broadband lines such ascable broadband lines, optical broadband lines (e.g., fiber), DSLbroadband lines, etc., each being represented here as access line 335.The access node 350 returns current operational data and currentoperating conditions regarding the broadband lines or access line 335 tothe Virtual Network Function implemented by the cloud, PoP, or datacenter 310 over the control plane interface 385.

Virtual Network Function 380 analyzes the returned operational data andoperating conditions and then issues instructions to the access node toadopt configurations, adopt configuration parameters or operationalparameters, modes, thresholds, etc., adopt or implement calculatedcoefficients provided by the virtual network function 380, implementscheduling schemes specified by the virtual network function 380, and soforth.

The Access node 350 will then responsively adopt or carry out theinstructions provided by the virtual network function 380. In additionto scheduling and configuration means, a Persistent Management Agent(PMA) is also provided such that if the various network elements arepowered off, their configuration will nevertheless be maintained andthus persist through the power cycle or extended power off period, thuspotentially negating the need for a re-configuration and re-training, orworse yet, extended downtime and network unavailability to the end user.

FIG. 4 depicts an alternative exemplary architecture 400 in accordancewith described embodiments, and more particularly, an exemplarymigration from a Physical Network Function (PNF) to a Virtualized AccessNode Function or a Virtualized Network Function (VNF). For instance,there are multiple CPEs 490 depicted, each communicatively interfacedwith the various Physical Network Functions (PNF) 401, 402, 406 and 407.In the case of PNF 403, the CPEs 490 are only indirectly connected asPNF 403 is connected to the CPEs through an aggregation of PNF 401 and402, which are then connected with backhaul 430A, to form the internalphysical access node functions 498 depicted. Conversely, the lowerportion of the CPEs 490 are connected with PNF 406 and PNF 407respectively, which in turn are connected via backhaul 430B to theVirtualized Access Node Function (VANF) 408 accessible via network(s)455, thus constituting the virtualized access node functions 499. Insuch a way, functions may be migrated, abstracted, etc., from being aphysical network function (PNF) such as 406 and 407 internal to anAccess Node (AN) 455 to being a Virtualized Access Node Function (VANF)408.

Virtualized Access Node Functions (VANFs) may be thought of as PhysicalNetwork Functions (PNFs) that are moved out of the physical access node,located remotely, and then which are made to communicate with thephysical access node. The VANFs can replace or complement PhysicalNetwork Functions (PNFs) that physically remain on the physical accessnode. Such an external VANF can be considered logically to be a part ofthe access node notwithstanding its remote presence.

A VANF may run or execute upon virtualized infrastructure constructed ofhardware and software. This virtualized infrastructure may span acrossone or several locations, such as locations of different servers, racks,data centers, points-of-presence (PoPs), or a cloud. A physical orvirtual network may provide connectivity between these locations. Alayer of software running on the hardware infrastructure may providevirtual machines, virtual infrastructure, a virtual platform, virtualsoftware, or other virtual services that create the virtualizedinfrastructure that the VANF is deployed on, The VANF or VANFs may becontrolled by one or more of: a hypervisor, an orchestrator, aVirtualized Network Function Manager, and a Virtualized InfrastructureManager.

FIG. 5 depicts an alternative exemplary architecture 500 in accordancewith described embodiments, and more particularly, depicts theinterfacing of virtualized access node functions (e.g., VANFs) withmultiple service providers. Depicted here is a functions abstractionlayer 501 cable of converting signaling and mediating between serviceproviders 505A and 505B and the requests of such service providers 505Aand 505B as well as performing resource allocation amongst them. Theservice providers 505A and 505B interface 510 through the functionsabstraction layer 501 to various network elements 515 through variousproprietary or standard interfaces 520 according to the depictedembodiment. Any or all of the depicted network elements 515 NetworkElements 515 may include transceivers or receivers and transmitters forcommunicating data onto the broadband lines. For instance, DPUs, DSLAMs,CPEs, and other access nodes may embody such transceivers orreceivers/transmitters for communicating data.

Communication between service providers, VANFs, access nodes, and othersystems, devices, or infrastructure may be passed through such afunctions abstraction layer 501 which maps between different signalingformats as depicted, all of which may utilize a common interface 510.

In some areas where multiple service providers are present, there may bean infrastructure provider that is in control of the wires, cables, oroptical fibers. In such embodiments, there may be one or more accessnode operators that are in control of the access nodes, and one or moreretail service providers which sell the broadband services to end-users.The infrastructure provider and access node operator may additionallyexist as one entity, called a “wholesale provider.”

VANFs facilitate such multi-provider environments, since the virtualizedfunctions may be used by multiple parties, and because there may bemultiple instances of each VANF without conflict. Various functions mayor may not be virtualized, and such virtualized functions may or may notbe shared by multiple providers. A retailer provider may be able toaccess VANFs from the wholesale provider and such a retail provider maybe able to instantiate a VANF on infrastructure owned by a wholesaleprovider.

VANFs may support both physical local loop unbundling (LLU) and virtualloop unbundling (VULA). “Super” VULA may likewise be enabled whichunbundles VANFs as well as physical infrastructure, and may thus providea level of unbundling such that a retail provider is enabled to performoperations similar to the way they would with physical unbundling.

Further enabled are various forms of metallic access. Fiber to the Node(FTTN) and Fiber to the distribution point (FTTdp) architectures utilizecopper only over the last few hundred or thousand meters from a remoteDigital Subscriber Line Access Multiplexer (DSLAM) or Distribution PointUnit (DPU), extending fiber nearly to the customer while avoiding theconsiderable cost of installing fiber into a customer premises. Theremote DSLAM or DPU is a very small, low-power device which needs to beenergy efficient. It may therefore be particularly advantageous tovirtualize computationally complex control and management functions forFTTdp DPUs which tend to consume more extensive amounts of electricpower due to their computationally intensive operations. VANFs canremove powering of some functions from FTTdp DPUs, and can involve powerefficiencies by statistical multiplexing functions across multiple linesor multiple groups of transceivers.

Further still, VDSL implementations, which includes VDSL1, VDSL2, andvectored VDSL, is generally used for FTTN and FTTdp deployments.Virtualized Access Node Functions (VANFs) for VDSL may include, by wayof example: VDSL Low-Power Mode (LPM) Power Control Entity (PCE) forwhich there are a number of thresholds and other settings that may bevaried to configure VDSL LPM on individual transceivers. Also, VANFs candetermine primitives that indicate LPM entry or exit. These settings andprimitives may be determined in a virtualized power control entity andcommunicated to the transceivers. The transceivers may also feedback theLPM state and various test and diagnostics to the virtualized powercontrol entity, all of which offloads processing from the field deployednetwork elements and thus improves energy consumption as well asproviding various other benefits described herein.

VANFs for VDSL may further include control and management ofshowtime-adaptive virtual noise or autonomous virtual noise. With suchtechniques, a transceiver retains data about time-varying noise andthese data are then used to determine bit-loading. For example, a peakor semi-peak level of noise may be estimated and then the noise estimateused for determining bit-loading may assume this level of noise.Alternatively, the bit-loading, margin, transmit power, or PowerSpectrum Density (PSD) may be directly set using the time-varying noisedata. These data may also be sent to a virtualized bit-loading/noiseestimation function, which then communicates a calculated set of noiseestimates, showtime-adaptive virtual noise, threshold settings, orbit-loading back to the field deployed transceiver. One use of such atechnique is to maintain stability with crosstalk from lines using LowPower Mode (LPM), other uses include time-varying radio noise and noisefrom Power-Line Carrier (PLC) systems.

VANFs for VDSL may further include virtualized management of vectoring,which cancels crosstalk. Any of the following management parameters maybe communicated from the VANF to the transceivers or Vectoring ControlEntity (VCE) to configure vectored VDSL: Vectoring frequency-bandcontrol (VECTOR_BAND_CONTROL), FEXT cancellation Line Priorities(FEXT_CANCEL_PRIORITY), FEXT cancellation enabling/disabling(FEXT_CANCEL_ENABLE), Vectoring Mode Enable (VECTORMODE_ENABLE). Furtherstill, transmit power and PSD may be set. The transceivers may alsofeedback test and diagnostics data, including FEXT coupling (XLIN) tothe virtualized vectoring management.

VANF for VDSL may further include virtualized Vectoring Control Entity(VCE). The vector precoder (downstream) or receiver canceller (upstream,multiplies and sums signals on multiple lines by vectoring coefficientsto cancel crosstalk). The vectoring coefficients may be computed in sucha virtualized VCE VANF. The cancellation itself then occurs using thesecoefficients in the transceivers, for instance, by instructing thetransceivers to adopt the provided coefficients. Vectoring error samplesmay be transmitted from the transceivers to the virtualized VCE throughthe network, and then the virtualized VCE communicates vectorcoefficients back to the transceivers. The vectoring error samples maybe averaged, sub-sampled, or both to lower their traffic load on thenetwork. Also, the VANF may rapidly compute, or pre-compute, newcoefficients when lines join or leave the vectored group.

FIG. 6 depicts an alternative exemplary architecture 600 in accordancewith described embodiments, and more particularly, depictsimplementations of various optional Virtualized Persistent ManagementAgent (VPMA) locations. Depicted within the network cloud 605 are datacenter 645 having therein VPMA 620A, Operations Support Systems (OSS)630 having therein VPMA 620B, and lastly the Element Management System(EMS) 625 having therein VPMA 620C, the network cloud 605 beingconnected to the access node aggregation device 610 via backhaul 670.The access node aggregation device 610 includes VPMA 615 and the accessnode aggregation device 610 is communicably interfaced to each of thetwo access nodes 655 depicted which in turn are connected with CPEs 690.

Further enabled are various forms of metallic access FTTdp and G.fast.FTTdp uses either G.fast or VDSL, or both, for the final transmissionover metallic cables. The “DSLAM” equivalent network element in FTTdpimplementations is referred to as a “DPU.” Regardless, the same VANFsdefined for VDSL may apply to G.fast or FTTdp, plus additionalfunctions. For instance, VANFs for G.fast may include trafficscheduling, power management and vectoring as well as the Virtual G.fastPersistent Management Agent (VPMA) elements (e.g., 615 and 620A-C)depicted here.

G.fast traffic, power, and vectoring management are still furtherenabled in that G.fast uses Time-Division Duplex (TDD) where a givenline may be transmitting data, idle, or quiet in each symbol period ineach direction of transmission (upstream and downstream). G.fast mayimplement “discontinuous operation” for power control. Withdiscontinuous operation, the optimal vectoring coefficients andbit-loading change rapidly.

Therefore, G.fast implementations may utilize any of the followinginterrelated constructs: Dynamic Rate Allocation (DRA) which may changethe upstream/downstream asymmetry ratio, and schedule the times in whicheach line is transmitting data, dummy, idle, or quiet symbols; PowerControl Entity (PCE) which controls low-power modes or states; vectoringcoefficients which are generally determined by the VCE; and setting thebit-loading of each line which may optionally be controlled from thetransmitter. Baseline bit-loading tables may be determined by thevirtualized management system. Signal to Noise Ratio (SNR) margin mayadditionally be varied to indirectly vary bit-loading. Theper-subcarrier gains, gi, may similarly be set.

To facilitate transceiver power savings, discontinuous operation may beenabled for G.fast, where not all of the time available for datatransmission is used, and where power is saved by turning offtransceiver functions the remainder of the time. With discontinuousoperation, symbol periods in a logical frame may be filled with eithernormal data symbols, dummy symbols, idle symbols, or quiet symbols. Insuch embodiments, a Robust Management Channel (RMC) symbol is consideredto operate similar to data symbols, and a pilot symbol is considered tooperate as a type of dummy symbol.

FIG. 7 depicts a flow diagram of a method 700 for implementing a VANFalgorithm for traffic, power, and vectoring management. For instance,traffic allocation, vectoring coefficients, bit-loading, bit rates, andpower savings are calculated by the VANF at each step in accordance witha particular embodiment. For example, a G.fast discontinuous operationprocess flow may be performed via the method 700 depicted, including thecoordination of G.fast discontinuous operation across multiple linesimplemented via a Virtualized Access Node Function (VANF). Method 700may be performed by processing logic that may include hardware (e.g.,circuitry, dedicated logic, programmable logic, microcode, etc.),software (e.g., instructions run on a processing device) to performvarious operations such as managing, controlling, analyzing, collecting,generating, monitoring, diagnosing, executing, presenting, receiving,interfacing, communicating, receiving, transmitting, processing,providing, determining, triggering, displaying, retrieving, updating,sending, returning, etc., in pursuance of the systems and methods asdescribed herein. For example, system(s) 170 as depicted at FIG. 1, theManagement, Systems, Controller(s) 215 as depicted at FIG. 2, thearchitecture 800 as depicted at FIG. 8, systems 900 and 1100 at FIGS. 9and 11 respectively, or the machine 1300 at FIG. 13, may implement thedescribed methodologies. Some of the blocks and/or operations listedbelow are optional in accordance with certain embodiments. The numberingof the blocks presented is for the sake of clarity and is not intendedto prescribe an order of operations in which the various blocks mustoccur.

As depicted, processing starts and progresses to block 701 whereprocessing logic adds idle or dummy symbols to each frame until alllines are in normal operation. At decision point 702, it is determinedwhether sufficient bit rates and power savings are attained, and if so,then flow proceeds to the end. Otherwise, flow progresses to block 703where processing logic attempts a normal operation interval plusnon-overlapping transmissions on all lines in discontinuous operation.At decision point 704, it is determined whether sufficient bit rates andpower savings are attained, and if so, then flow proceeds to the end.Otherwise, flow progresses to block 705, where processing logic attemptsa normal operation interval plus N overlapping time intervals indiscontinuous operation (e.g., starting with N=1). At decision point706, it is determined whether sufficient bit rates and power savings areattained, and if so, then flow proceeds to the end. Otherwise, twooptions are permissible. If sufficient bit rates and power savings arenot attained and N<NMAX (e.g., N is less than the permissible NMAXthreshold), then flow increments N and block 705 is re-attempted.Otherwise, if sufficient bit rates and power savings are not attainedand N>=NMAX (e.g., N is greater than or equal to the permissible NMAXthreshold), then flow instead advances to block 707 where processinglogic attempts changing bit-loading to accommodate non-optimal vectoringcoefficients. At decision point 708, it is determined whether sufficientbit rates and power savings are attained, and if so, then flow proceedsto the end. Otherwise, processing returns to block 701 where the method700 may be performed for another iteration.

Notably, the calculations may be performed offline by the VANF withoutburdening the field deployed access nodes, such that the VANF mayidentify and submit to the access node a suitable configuration to thefield deployed access node for adoption or at least to attempt the newconfiguration and report back operational data and conditions subsequentto use of the new configuration.

Power management involves complex tradeoffs in delay, vectoringperformance, and power usage, and various scenarios may be examined andoptimized in a VANF without burdening the field deployed networkelements.

Vectoring cancels crosstalk and the optimal vectoring coefficientschange when any one or more lines is transmitting or not transmitting.Stated differently, in any symbol period, there is a set of lines thatare transmitting data, dummy, or idle symbols; and a set of lines thatare quiet. If these sets of lines change, then the optimal vectoringcoefficients change. To accommodate this, the vector coefficients maychange with any change in the membership of these sets, or thebit-loading and margin may be configured so that the performance impactfrom using non-optimal vectoring coefficients is acceptable.

As scheduling and vectoring interact, for example, symbols may bescheduled for transmission so that they are in different time slots ineach line in discontinuous operation to avoid needing to use vectoringin those time slots.

A G.fast Transmission Unit is referred to as an “FTU,” and furtherstill, a Network-end G.fast Transmission Unit is an “FTU-O” where as aCustomer-end G.fast Transmission Unit is a FTU-R. When vectoring isenabled with discontinuous operation, both FTU-O and FTU-R support aseparate baseline bit-loading table for each of the intervals, such as abit-loading table for normal operation interval and a bit-loading tablefor the discontinuous operation interval. The baseline bit-loading tablemay be changed by sending Embedded Operations Channel (EOC) commandsacross the G.fast line. Transmitter-initiated gain adjustment (TIGA) maybe used to change the active bit-loading and gain compensation factor atthe remote unit (FTU-R). Using these mechanisms, the DRA function maycontrol the configuration of the active bit-loading table and gainstable.

Performance, throughput, and power usage all vary in a complex set ofdependencies of these. For example, a line may suddenly have very littletraffic to send, then the DRA may set the line to send quiet symbols (be“off”) for most of the TDD frame. To satisfy traffic demand on otherlines, the DRA may then change transmission opportunity allocations ofother lines and even vary the upstream/downstream asymmetry ratio. TheVCE may then need to change vectoring precoder coefficients, and to makethis implementable it may then change some of the quiet symbols to beidle symbols that transmit vectoring cancellation signals. This thenimpacts the power usage and may further interact with the DRA. All ofthese considerations apply to both upstream and downstream.

The results of these interactions are not intuitive, but they may beanalyzed offline, with optimal or improved settings selected, andcommunicated to the DPU and transceivers for adoption. A VANF spanningDRA, PCE, and VCE functions may run through a series of candidateconfigurations for each situation, calculate the resulting performances,and power usage, and select a good trade-off. These trade-offs may beiteratively optimized. The desired tradeoffs may be selected by theoperator or provider, and configured through the virtual managementengine. These calculations may be prohibitively complex to be performedin a field deployed network element, yet may readily be computed withinthe compute infrastructure of a data center supporting such fielddeployed network elements via VANF.

Referring back to FIG. 6, Virtual G.fast Persistent Management Agent(VPMA) may virtualize the “Persistent Management Agent (PMA)” so as tostore configuration and diagnostics data for a DPU and provide access tosuch information even when the DPU is powered down due to lack of allpower from Reverse Power Feed (RPF), or other operating conditions whichinterrupt the field deployed DPUs ability to maintain its ownconfiguration. The persistence of the PMA also makes it useful forperforming a number of related management functions. The PMA can alsoaccept configuration changes from management systems when the DPU is notpowered.

Conventional solutions which provide PMA capabilities embed PMA into thenetwork elements themselves, however, the PMA may be abstracted and thenvirtualized into a virtualized PMA (VPMA), which is itself another typeof VANF. Some PMA functions may be virtualized and be VANFs, and somePMA functions may remain as physical network functions (PNF). The VPMAfundamentally differs from a PMA in that it may access a great amount ofcomputing resources and in doing so provide a greater depth offunctionality.

VPMA functions may be located in various locations as shown in FIG. 6.The VPMA functions may be a virtualized part of an EMS 625 or ElementManagement Function (EMF), an Operation Support System (OSS) 630 orNetwork Management System (NMS) or the VPMA may operate as a stand-aloneVNF.

VPMA functions for FTTdp and G.fast may thus include any of: persistentstorage of DPU configuration settings and diagnostics information, whichmay be accessed even when the DPU is powered down; and permitting theVPMA settings to be changed by other management systems when the DPU ispowered down and then communicated to the DPU when it powers back up.Additionally, other management systems may read diagnostics data fromthe VPMA when the DPU is powered down. VPMA functions for FTTdp andG.fast may further include control and management of reverse power feed(RPF) including interpretation by the VPMA of dying gasp messages fromthe DPU or the transceivers, where the dying gasp may indicate differentreasons for power-down (e.g., customer switched off modem, a wire fault,a mains power failure, etc.).

VPMA functions for FTTdp and G.fast may further include so called “ZeroTouch” Operations, Administration and Management (OAM) configuration,where connections to new subscribers may be made automatically insteadof being done by a technician. The VPMA controls connections from theDPU to the subscribers and such subscribers may be connected totransceiver ports directly, or they may be connected to a switch matrixwhich connects a line to a transceiver port when a subscriber requestsservice.

VPMA functions for FTTdp and G.fast may further include management ofG.fast low power modes (LPM), using cross-layer data and control.Indications from higher-layers of sessions, resource allocation, trafficlevels, queue occupancy, etc., provide data that is used by analyses inthe VPMA to determine if G.fast should be in LPM, what type of LPM touse, and what LPM configuration settings to use. Also, the G.fast LPMconfiguration data may then be returned back to the higher layersfunctions such as resource allocation and policy management.

In addition to the VPMA functions for FTTdp and G.fast, the VPMA maysubsume functions listed previously for VDSL; including DRA, powercontrol, vectoring control, bit-loading, and gains.

FIG. 8 depicts an alternative exemplary architecture 800 in accordancewith described embodiments, and more particularly, depicts an exemplaryinternal architecture 800 of the Virtualized Access Node Functions(VANFs), including infrastructure management and orchestration. TheOSS/NMS 801 provide the operational support system and networkmanagement system functions respectively. Orchestrator 802 controls theinteractions between the virtualization functions and additionallymanages network services across a provider's domain and orchestratesresource and usage co-existence across multiple VNF instances.

EMS 803 provides the element management system; VANF 804 and 805 providethe Virtualized Access Node Functions. VANF lifecycle manager 806manages VANFs, including: VANF instantiation, termination, configurationof resources, VANF updates, performance, and coordination with EMS.Virtualized infrastructure manager 807 controls and manages the compute,storage, and network resources within the compute infrastructure 810depicted separately.

Within the compute infrastructure 810 there is depicted virtual storage811, virtual network 812, virtual computing 813, a virtualization layer814, all of which is supported by the hardware of the computeinfrastructure 810, including storage hardware 815, network hardware816, and computing hardware 817.

For instance, a VANF 804 or 805 may utilize such an algorithm or method700 as is depicted at FIG. 7 to run through many “what if” scenarios andidentify an acceptable or optimal operating point or a set of operatingparameters. Traffic allocation, vectoring coefficients, bit-loading,gains, bit rates, and power savings of each line are calculated by theVANF 804 or 805 at each step without incurring computational burden forthe field deployed access node, and potentially performing processingwhich is not only burdensome to the field deployed access node, but inmany instances is beyond the computing capabilities of such an accessnode. The output of the algorithm or method 700 determines theconfiguration to be used by the access node, DPU, Dynamic RateAllocation (DRA), or Vectoring Control Entity (VCE).

Other variants of the algorithm described may be performed by the VANF804 or 805 to determine the allocation of time slots, transmissions,vectoring, bit-loading, and gains. Given a number N of overlapping timeintervals, there may likewise be a search across different possibletimes of the overlapping and non-overlapping time intervals and theremay be a non-overlapping time interval as well as partially-overlappingtime intervals. Further still, different stopping criteria may beutilized rather than those expressly set forth by the method 700.

Other broadband functions that may be part of VANFs 804 and 805 includeany of the following extensions, such as services differentiation,allocation of Quality of Service (QoS) and Class of Service (CoS)levels; Dynamic Spectrum Management (DSM), and control and management ofbroadband access by the consumer using apps or software agents.

VANFs 804 and 805 may be centrally implemented on a singleinfrastructure or implemented in a distributed fashion across disparateinfrastructure.

The BNG/BRAS (e.g., refer to element 220 at FIG. 2) and the CPE (e.g.,any of 250A-F at FIG. 2), may also perform broadband access networkcontrol and management which may be virtualized in conjunction withVANFs.

Service chaining, using multiple chained or in parallel VANFs andVirtualized Network Function Components (VNFC). Such service chainingmay be controlled by an orchestrator 802 or equivalent orchestrationfunction. For example, a first VANF 804 or 805 may input diagnosticsdata; a second VANF 804 or 805 analyzes this data; and then a third VANFuses the analysis results to reconfigure an access node, system, line,or transceiver.

VANFs 804 or 805 may work in conjunction with Software-DefinedNetworking (SDN) controllers.

VANFs 804 or 805 may also involve related functions, systems, andinterfaces; such as inventory, plant records, OSS-EMS interfaces, andbusiness-to-business interfaces.

Passive Optical Networks (PON) terminate many access lines on an OpticalLine Terminal (OLT). The OLT is central in performing many layer 2functions such as scheduling, implementing policy, assigning bit rates,and traffic allocations. Determination of Dynamic Bandwidth Allocation(DBA), time slot assignments, and wavelength assignments may bevirtualized. Fiber diagnostics may also be virtualized. Other multi-linefunctions are currently physical functions in the OLT. Many such opticalaccess functions may be virtualized and become VANFs.

Cable Modem Termination Systems (CMTS) terminate many cable modem lines.The CMTS performs many functions such as scheduling, implementingpolicy, assigning bit rates, and traffic allocations. The CMTS is alsocentral to functions among multiple lines. Radio Frequency (RF) channelassignments and multi-channel bonding control, and diagnostics relatedto RF or fiber performance may be virtualized. Many such cable-basedfunctions may be virtualized and become VANFs.

Regardless of the type of broadband line or particular physical media;test, diagnostics, monitoring and troubleshooting analyses may bevirtualized. Large-scale computing resources and databases storinglong-term history in data centers or the cloud may perform deep analyseswell beyond what is computationally feasible via the field deployedaccess nodes themselves. These may input monitoring data, test data,performance data, diagnostics data, and line or equipment status data.The inputs are analyzed by the VANF 804 or 805 to spot faults, identifypoor performance, monitor Quality of Service (QoS), monitor Quality ofExperience (QoE), issue alarms, determine root cause, assist introubleshooting, and sometimes also recommend remediation actions. VANFanalysis outputs may be used for off line monitoring or real-time test.

The VANF 804 or 805 may react to perform diagnostics, analyses, orreconfigurations in response to inputs from other systems or persons. Aconsumer may provide feedback indicating their customer satisfaction ortheir experience with their service quality which then triggers actionsin a VANF. The consumer's feedback may be directly provided to a VANF804 or 805, or the feedback may be analyzed by further systems or VANFs804 or 805. This may result in generating remediation instructions, orgenerating a trouble ticket to notify another system, or it may resultin a VANF re-configuring an access node, line, or transceiver. Suchcustomer feedback may be input to a VANF one time, or multiple repeatingtimes. Similarly, a service provider or monitoring system may estimatecustomer satisfaction and input this estimate to a VANF to triggerfurther actions.

FIG. 9 illustrates a diagrammatic representation of a system 900 (e.g.,for access node virtualization) in accordance with which embodiments mayoperate, be installed, integrated, or configured.

In accordance with one embodiment, there is a system 900 having at leasta processor 996 and a memory 995 therein to execute implementing logicand/or instructions 960. Such a system 900 may communicatively interfacewith and cooperatively execute with the benefit of a hosted computingenvironment, such as an on-demand service provider, a cloud basedservice provider, or any entity which operates remotely from the networkelements having functions being abstracted and virtualized by the remotesystem, in which the network elements are communicably interfaced over anetwork, such as a public Internet.

According to the depicted embodiment, system 900 further includes acontrol plane interface 930 to communicably interface the system with anaccess node 978 over a network (see element 977 to access node), inwhich the access node 978 is physically coupled with a plurality ofbroadband lines 979. Such a system 900 further includes a virtualizedmodule 945 to provide a virtualized implementation 946 of a plurality offunctions 980 of the access node 978 at the system 900, in which thevirtualized module 945 executes on a virtualized computinginfrastructure 944; in which the control plane interface 930 of thesystem 900 is to receive current operational data and current operatingconditions 981 for the plurality of broadband lines 979 from the accessnode 978; and in which the virtualized module 945 is to update thevirtualized implementations 946 of the plurality of functions 980 of theaccess node 978 at the system 900 according to the current operationaldata and the current operating conditions 981 received from the accessnode 978. Such a system 900 further includes an analysis module 935 toanalyze the current operational data and the current operatingconditions 981 received from the access node 978 and an instructionmodule 925 to generate control parameters 982 to affect operation of theaccess node 978 based on the analysis of the current operational dataand the current operating conditions 981 received; and further in whichthe control plane interface 930 is to send the control parameters 982 tothe access node for adoption at the access node 978.

Network Functions Virtualization Infrastructure (NFVI) providesalternative means by which to implement the virtualized computinginfrastructure 944 of the system 900. Regardless, Virtualized NetworkFunctions (VNFs) execute upon the virtualized computing infrastructure944 of the system 900 remote from the access nodes 978 from where therespective functions 980 originate. For instance, a virtualized view ofthe computing resources of the access node 978 is made available locallyat the system 900, pulled in by the virtualized module 945.

In accordance with another embodiment of system 900, the virtualizedmodule includes a Virtualized Network Function (VNF) module running on aNetwork Functions Virtualization Infrastructure (NFVI), and controlledby one or more of a Virtualized Network Function Manager (VNFM); and aNetwork Function Virtualization Orchestrator (NFVO).

In accordance with another embodiment of system 900, the control planeinterface to send the control parameters to the access node for adoptionat the access node includes the control plane interface to instruct theaccess node to adopt the control parameters sent as a new operatingconfiguration.

In accordance with another embodiment of system 900, the access nodeembodies one of: a Digital Subscriber Line Access Multiplexer (DSLAM); aDistribution Point Unit (DPU); an Optical Line Terminal (OLT); and aCable Modem Termination System (CMTS).

In accordance with another embodiment of system 900, the system embodiesVirtualized Network Function (VNF) server functionality physicallyremote from the access node and in communication with the access nodevia the network.

In accordance with another embodiment of system 900, the VNF serverfunctionality is implemented by a third party service provider differentthan a broadband Internet operator that owns and is responsible fornetworking equipment to operate the plurality of broadband lines anddifferent than a broadband services provider responsible for providingbroadband communication services to broadband service customers; and inwhich the VNF server communicably interfaces to the access node over apublic or private Internet through broadband networking elements of thebroadband system operator or the broadband services provider.

Such a broadband services provider may be a provider of DSL, cable,broadband, fiber access, or G.fast, type broadband services, etc.

In accordance with another embodiment of system 900, the third partyservice provider provides network virtualization services for the accessnode and the plurality of DSL lines within a DSL network as asubscription based cloud service.

In accordance with another embodiment of system 900, the plurality ofbroadband lines include a plurality of Digital Subscriber Lines (DSLlines) of a DSL network.

In accordance with another embodiment of system 900, the virtualizedmodule is to virtualize functions of a broadband access node by definingone or more external interfaces the functions as they correspond to thebroadband access node's functions, in which the defined one or moreexternal interfaces and the functions are to be deployed into avirtualized infrastructure within which the system operates.

In accordance with another embodiment of system 900, virtualized modulevirtualizes functions of a broadband access node, the functions beingselected from the group including: a Persistent Management Agent (PMA)function; a Dynamic Rate Allocation (DRA) function; a Power ControlEntity (PCE) function; a Vectoring Control Entity (VCE) function; amanaging Remote Power Feed (RPF) function; a derived telephonymanagement function; a zero-touch Operations, Administration, andManagement (OAM) function; Class of Service (CoS) assignment functions;Quality of Service (QoS) monitoring functions; one or more functions tosupport, interpret, and handle dying gasp messages from transceivers;one or more functions to perform Dynamic Spectrum Management (DSM); oneor more functions to implement control of a baseline bit-loading table;one or more functions to implement control of an active bit-loadingtable; one or more functions to implement control of sub-carrier gains;one or more functions to implement control of a bit rates and SNRmargins; one or more functions to support consumer specified, provided,or managed applications that are to execute locally within the system orexecute remotely from the system and interface back to the system; andone or more functions to perform diagnostics.

In accordance with another embodiment of system 900, the virtualizedmodule virtualizes functions for one or more of: an Asymmetric DigitalSubscriber Line (ADSL) implementation; an ADSL1 implementation; an ADSL2implementation; an ADSL2plus implementation; a Very high speed DigitalSubscriber Line (VDSL) implementation; a VDSL1 implementation; a VDSL2implementation; a vectored VDSL implementation; a G.fast implementation;a Fiber to the Node (FTTN) implementation; a Fiber to the DistributionPoint (FTTdp) implementation; a Passive Optic Networks (PON)implementation; a Gigabit PON (GPON) implementation; a Next-GenerationPON (NGPON) implementation; a 10-Gigabit capable PON (XG-PON)implementation; a Ethernet PON (EPON) implementation; a 10 Gigabit PON(10GEPON) implementation; a point-to-point Ethernet on fiberimplementation; and a Cable Modem Termination System (CMTS)implementation.

In accordance with another embodiment of system 900, the virtualizedmodule virtualizes functions for a network of Very high speed DigitalSubscriber Lines (VDSL); and in which the virtualized module performsone or more of: (i) power management and control of low-power linkstates for the network of VDSL lines, (ii) Control and management ofshowtime-adaptive virtual noise or autonomous virtual noise on thenetwork of VDSL lines, (iii) Vectoring management on the network of VDSLlines, and (iv) Vectoring Control Entity (VCE) for the network of VDSLlines.

In accordance with another embodiment of system 900, the virtualizedmodule virtualizes functions for at least one of: managing traffic;managing power; vectoring for G.fast; and determination over multiple ofthe broadband lines via one or more of: Dynamic Rate Allocation (DRA),discontinuous operation, power control, vectoring control, baselinebit-loading tables, active bit-loading tables, per sub-carrier gains,and Transmitter-Initiated Gain Adjustment (TIGA).

In accordance with another embodiment of system 900, the virtualizedmodule implements a Virtual Persistent Management Agent or a VirtualG.fast Persistent Management Agent to persistently store diagnostics, topersistently store configuration information, to control and managereverse power feed (RPF) information, to control connections from aDistribution Point Unit (DPU) to subscribers connected with thebroadband lines, and/or to manage G.fast Low Power Modes (LPMs).

In accordance with another embodiment of system 900, the virtualizedmodule virtualizes functions for a Passive Optical Network (PON) or anOptical Line Terminal (OLT), in which the virtualized functions of thePON or the OLT are to perform one or more of: Dynamic BandwidthAllocation (DBA); Time-slot allocation and scheduling for differentusers and different traffic types; and wavelength assignments inWavelength-Division Multiplexed (WDM) implementations or hybridWDM/time-division PON implementations.

In accordance with another embodiment of system 900, the virtualizedmodule virtualizes functions for a Cable Modem Termination System(CMTS), in which the virtualized functions of the CMTS are to performone or more of: time-slot allocation; time-slot scheduling; time-slottraffic management; radio Frequency (RF) channel assignment; control ofQuadrature Amplitude Modulation (QAM); and control of channel bonding.

In accordance with another embodiment of system 900, the virtualizedmodule virtualizes interfaces that enable Virtual Unbundled Loop Access(VULA).

In accordance with another embodiment of system 900, the analysis module935 is to analyze one or more of test parameters, performance monitoringparameters, diagnostics parameters, and status parameters; and in whichthe analysis module is to further monitor Quality of Service (QoS),monitor Quality of Experience (QoE), monitor issuing alarms, analyzeinputs to determine root cause and inform troubleshooting operations viaanalysis output.

In accordance with another embodiment of system 900, the analysis moduleis to analyze input diagnostics or analyses output and responsivelygenerate at least one of: a recommend remediation or corrective action;a trouble ticket; a reconfiguration for the access node; a linereconfiguration; and a transceiver re-configuration.

In accordance with another embodiment of system 900, the control planeinterface to send the control parameters to the access node for adoptionat the access node includes the control plane of the system to interactwith at least one of: a Physical Network Function (PNF); a BroadbandNetwork Gateway (BNG); a Broadband Remote Access Server (BRAS); aCustomer Premises Equipment (CPE); a Residential Gateways (RGs); aSoftware-Defined Networking (SDN) controller; one or more Managementsystems; one or more Operations Support Systems (OSS); one or moreBusiness Support Systems (BSS); and one or more Element ManagementSystems (EMS).

In accordance with another embodiment of system 900, the virtualizedmodule provides the virtualized implementation of the plurality offunctions of the access node within a virtual machine to execute on thesystem, in which the virtual machine is to be backed up onto persistentstorage as an archive, and in which the virtual machine isredistributable to other systems capable of executing the virtualizedimplementation of the plurality of functions of the access node.

In accordance with another embodiment of system 900, the virtualizedmodule provides the virtualized implementation of the plurality offunctions of the access node either centralized within a singleinfrastructure or distributed across disparate infrastructure.

In accordance with another embodiment of system 900, the virtualizedmodule provides the virtualized implementation of the plurality offunctions of the access node via service chaining with either multiplechained Virtualized Network Function Components (VNFCs) or withinparallel VNFCs, the VNFCs being controlled by an orchestration functionexposed at the system.

In accordance with another embodiment of system 900, the virtualizedmodule is to perform reconfigurations responsive to an input having ameasure of consumer satisfaction therein, the measure of consumersatisfaction constituting one or more of: consumer input; an estimate ofconsumer satisfaction determined by a monitoring system; an estimate ofconsumer satisfaction determined by a service quality management system;and an estimate of consumer satisfaction provided by a service provider.

In one embodiment, system 900 includes communication bus(es) 915 totransfer transactions, instructions, requests, test results, analysis,current operating conditions, diagnostics inputs and outputs, outgoinginstructions and configuration parameters, and other data within system900 among a plurality of peripheral devices communicably interfaced withone or more communication buses 915. The control plane interface 930 ofsystem 900 may further receive requests, return responses, and otherwiseinterface with network elements located separately from system 900.

In some embodiments, control plane interface 930 communicatesinformation via an out-of-band connection separate from DSL line basedcommunications, where “in-band” communications are communications thattraverse the same communication means as payload data (e.g., content)being exchanged between networked devices and where “out-of-band”communications are communications that traverse an isolatedcommunication means, separate from the mechanism for communicating thepayload data. An out-of-band connection may serve as a redundant orbackup interface over which to communicate control data between thesystem 900 and other networked devices or between the system 900 and athird party service provider. For example, control plane interface 930may provide a means by which to communicate with system 900 to provideor receive management and control related functions and information.

FIG. 10 depicts a flow diagram of a method 1000 for implementing thevirtualization of access node functions. Method 1000 may be performed byprocessing logic that may include hardware (e.g., circuitry, dedicatedlogic, programmable logic, microcode, etc.), software (e.g.,instructions run on a processing device) to perform various operationssuch as managing, controlling, analyzing, collecting, generating,monitoring, diagnosing, executing, presenting, receiving, communicablyinterfacing, virtualizing, updating, analyzing, sending, communicating,receiving, transmitting, processing, providing, determining, triggering,displaying, retrieving, returning, etc., in pursuance of the systems andmethods as described herein. For example, system(s) 170 as depicted atFIG. 1, the Management, Systems, Controller(s) 215 as depicted at FIG.2, the architecture 800 as depicted at FIG. 8, systems 900 and 1100 atFIGS. 9 and 11 respectively, or the machine 1300 at FIG. 13, mayimplement the described methodologies. Some of the blocks and/oroperations listed below are optional in accordance with certainembodiments. The numbering of the blocks presented is for the sake ofclarity and is not intended to prescribe an order of operations in whichthe various blocks must occur.

Method 1000 begins at block 1005 with processing logic for communicablyinterfacing a control plane interface of the system to an access nodeover a network, in which the access node is physically coupled with aplurality of broadband lines.

At block 1010, processing logic virtualizes a plurality of functions ofthe access node at the system.

At block 1015, processing logic provides a virtualized implementation ofthe virtualized functions of the access node via a virtualized module ofthe system, in which the virtualized module executes on a virtualizedcomputing infrastructure.

At block 1020, processing logic receives, via the control planeinterface, current operational data and current operating conditions forthe plurality of broadband lines from the access node.

At block 1025, processing logic updates the virtualized implementationof the plurality of functions of the access node at the system accordingto the current operational data and the current operating conditionsreceived from the access node.

At block 1030, processing logic analyzes, via an analysis module of thesystem, the current operational data and the current operatingconditions received from the access node.

At block 1035, processing logic generates, via an instruction module,control parameters to affect operation of the access node based on theanalysis of the current operational data and the current operatingconditions received.

At block 1040, processing logic sends, via the control plane interface,the control parameters to the access node for adoption at the accessnode.

According to another embodiment of method 1000, the virtualized moduleincludes a Virtualized Network Function (VNF) module running on aNetwork Functions Virtualization Infrastructure (NFVI), and controlledby one or more of a Virtualized Network Function Manager (VNFM); and aNetwork Function Virtualization Orchestrator (NFVO).

According to a particular embodiment, there is non-transitory computerreadable storage media, having instructions stored thereupon that, whenexecuted by one or more processors and memory of a virtualized cloudcomputing infrastructure, the instructions cause the system to performoperations including: communicably interfacing a control plane interfaceof the system to an access node over a network, in which the access nodeis physically coupled with a plurality of broadband lines; virtualizinga plurality of functions of the access node at the system; providing avirtualized implementation of the virtualized functions of the accessnode via a virtualized module of the system, in which the virtualizedmodule executes on the virtualized cloud computing infrastructure;receiving, via the control plane interface, current operational data andcurrent operating conditions for the plurality of broadband lines fromthe access node; updating the virtualized implementation of theplurality of functions of the access node at the system according to thecurrent operational data and the current operating conditions receivedfrom the access node; analyzing, via an analysis module of the system,the current operational data and the current operating conditionsreceived from the access node; generating, via an instruction module,control parameters to affect operation of the access node based on theanalysis of the current operational data and the current operatingconditions received; and sending, via the control plane interface, thecontrol parameters to the access node for adoption at the access node.

FIG. 11 illustrates a diagrammatic representation of a system 1100(e.g., a VANF implementation) in accordance with which embodiments mayoperate, be installed, integrated, or configured.

In accordance with one embodiment, there is a system 1100 having atleast a processor 1196 and a memory 1195 therein to execute implementinglogic and/or instructions 1160. Such a system 1100 may communicativelyinterface with and cooperatively execute with the benefit of a hostedcomputing environment, such as an on-demand service provider, a cloudbased service provider, or any entity which operates remotely from thenetwork elements having functions being abstracted and virtualized bythe remote system, in which the network elements are communicablyinterfaced over a network, such as a public Internet.

According to the depicted embodiment, system 1100 further includes avirtualized module 1145 operating on virtualized computinginfrastructure 1144, in which the virtualized module 1145 is to providea virtualized implementation 1146 of a plurality of functions 1180associated with one or more remotely located Distribution Point Units(DPUs) and/or Digital Subscriber Line Access Multiplexers (DSLAMs) 1178,each of the one or more remotely located DPUs and/or DSLAMs 1178 havinga plurality of broadband lines 1179 coupled thereto; in which thevirtualized module 1145 is to further control Persistent ManagementAgent (PMA) functions 1183 and control coordination of the one or moreremotely located DPUs and/or DSLAMs 1178 and the plurality of broadbandlines 1179 coupled with the one or more remotely located DPUs and/orDSLAMs 1178 by virtualizing one or more functions 1180 of the one ormore remotely located DPUs and/or DSLAMs 1178 to operate on thevirtualized computing infrastructure 1144. Such a system 1100 furtherincludes a network interface 1130 to receive data 1181 and to sendcontrol instructions 1182 for operation of the plurality of broadbandlines 1179 to and from the one or more remotely located DPUs and/orDSLAMs 1178.

In accordance with another embodiment of system 1100, the virtualizedmodule is to further communicate bi-directionally with the one or moreremotely located DPUs and/or DSLAMs.

In accordance with another embodiment of system 1100, the virtualizedmodule embodies a Virtualized Network Function (VNF) module to providethe virtualized implementation of the functions associated with one ormore remotely located DPUs and/or DSLAMs; in which the VNF module tooperate on the virtualized computing infrastructure of the systemincludes the VNF module to operate on a Virtualized Network FunctionInfrastructure (VNFI) using the processors and memory of thisinfrastructure; and in which the VNFI of the system virtualizes thefunctions of the one or more remotely located DPUs and/or DSLAMs locallyat the system.

In accordance with another embodiment of system 1100, the networkinterface is to communicably link the system with the one or moreremotely located DPUs and/or DSLAMs at least partially via a public orprivate Network; and in which the network interface includes a controlplane interface to communicably link the virtualized module of thesystem with the one or more remotely located DPUs and/or DSLAMs.

In accordance with another embodiment of system 1100, the control planeinterface of the system is to receive current operational data andcurrent operating conditions for the plurality of broadband lines fromthe one or more remotely located DPUs and/or DSLAMs via the public orprivate Internet.

In accordance with another embodiment, system 1100 further includes: ananalysis module 1135 to analyze the current operational data and thecurrent operating conditions received from the one or more remotelylocated DPUs and/or DSLAMs; and an instruction module 1125 to generatecontrol parameters to affect operation of the one or more remotelylocated DPUs and/or DSLAMs based on the analysis of the currentoperational data and the current operating conditions received.

In accordance with another embodiment of system 1100, the virtualizedmodule is to update the virtualized implementation of the plurality offunctions of the one or more remotely located DPUs and/or DSLAMs of thesystem according to the current operational data and the currentoperating conditions from the one or more remotely located DPUs and/orDSLAMs.

In accordance with another embodiment of system 1100, the virtualizedmodule is updated by an Element Management Systems (EMS) and/or aNetwork Management Systems (NMS) communicably interfaced with thevirtualized module of the system.

In accordance with another embodiment of system 1100, the EMS and/or NMSsends commands to the virtualized module of the system causing thevirtualized module to add or change services and/or settings on one ormore of the plurality of lines as represented within the virtualizedimplementation at the system; and in which the system further includesan analysis module to: (i) analyze the services and/or settings via thePMA functions, and (ii) control coordination of the one or more remotelylocated DPUs and/or DSLAMs by issuing commands to the one or moreremotely located DPUs and/or DSLAMs based on the analysis of theservices and/or settings.

In accordance with another embodiment of system 1100, each of theplurality of functions are selected from the group including: (i)zero-touch Operations, Administration, and Management (OAM) (ii) controland management of discontinuous operation, (iii) control and managementof Dynamic Rate Allocation (DRA), (iv) derived telephony management, (v)Reverse Power Feed (RPF) management, (vi) management of powerconsumption and low-power link states, (vii) vectoring control andmanagement, (viii) calculation of vectoring coefficients, (ix) layer 2and above functionalities, (x) management of showtime-adaptive virtualnoise, and (xi) control parameter determination.

In accordance with another embodiment of system 1100, the plurality offunctions include an integrated and coordinated determination over theplurality of broadband lines of one or more control parameters, the oneor more control parameters each selected from the group including:Dynamic Rate Allocation (DRA), discontinuous operation controlparameters, power control parameters, vectoring control parameters,baseline bit bit-loading tables, active bit-loading tables, persub-carrier gains control parameters, and transmitter-initiated gainadjustment (TIGA) control parameters.

In accordance with another embodiment of system 1100, the virtualizedmodule to control the PMA functions and coordination of the one or moreremotely located DPUs and/or DSLAMs includes: the virtualized moduleabstracting vectoring control from the one or more remotely located DPUsand/or DSLAMs, in which the vectoring control abstracted from the one ormore remotely located DPUs and/or DSLAMs is performed locally upon thevirtualized computing infrastructure via the virtualized module; and inwhich the system further includes the network interface to send controlinstructions for operation of the plurality of broadband lines to theone or more remotely located DPUs and/or DSLAMs, the controlinstructions specifying at least vectoring operations for the pluralityof broadband lines.

In accordance with another embodiment of system 1100, the virtualizedmodule further is to virtualize PMA functions abstracted from an OpticalLine Termination (OLT) unit communicably linked with any one of theremotely located DPUs and/or DSLAMs.

In accordance with another embodiment of system 1100, the one or moreremotely located DPUs embody a “Fiber To The distribution point”(“FTTdp”) unit which operates the plurality of broadband lines accordingto one any one of: a Very-high-bit-rate Digital Subscriber Line (“VDSL”)compliant communications standard; a G.fast compliant communicationsstandard; a G.vdsl compliant communications standard; an ITU-T G.9701compliant communications standard; or an ITU-T G.993.2 compliantcommunications standard.

In accordance with another embodiment, system 1100 further includes: thenetwork interface to send control instructions for operation of theplurality of broadband lines at any one of the remotely located DPUsaccording to any of G.fast, G.vdsl, VDSL, ITU-T G.9701, or ITU-T G.993.2compliant communications standards.

In accordance with another embodiment of system 1100, the virtualizedcomputing infrastructure is implemented by a cloud computing servicewhich operates in a geographic location different than the one or moreremotely located DPUs and/or DSLAMs, and in which the cloud computingservice is accessible to the one or more remotely located DPUs and/orDSLAMs over a public or private Internet.

In accordance with another embodiment of system 1100, the virtualizedcomputing infrastructure is implemented within a datacenter whichoperates in a geographic location different than the one or moreremotely located DPUs and/or DSLAMs, and in which the computinginfrastructure is accessible to the one or more remotely located DPUsand/or DSLAMs over a private network interface or a Virtual PrivateNetwork (VPN) interface.

For instance, large network operators may choose to utilize their owncloud-computing platform or data center, and their own network betweenthe cloud and the DPU/DSLAM rather subscribing to services provided by athird party. In such a case, the networking interconnect may be privateor operate via a VPN established over public and/or privatecommunication paths, and the cloud computing capabilities are notsubscription services at all for such a large entity, but rather, areinternally provided services.

In accordance with another embodiment of system 1100, the systemembodies a cloud computing interface accessible via a public or privateInternet, with the cloud computing infrastructure hosting virtualizedfunctions of the one or more remotely located DPUs and/or DSLAMsincluding indirect access to and indirect control of the one or moreremotely located DPUs and/or DSLAMs without requiring users of the cloudcomputing interface to directly access or directly authenticate to anyone of the one or more remotely located DPUs and/or DSLAMs.

In one embodiment, system 1100 includes communication bus(es) 1115 totransfer transactions, instructions, requests, test results, analysis,current operating conditions, diagnostics inputs and outputs, outgoinginstructions and configuration parameters, and other data within system1100 among a plurality of peripheral devices communicably interfacedwith one or more communication buses 1115. The network interface 1130(e.g., or a control plane interface according to select embodiments) ofsystem 1100 may further receive requests, return responses, andotherwise interface with network elements located separately from system1100.

FIG. 12 depicts a flow diagram of a method 1200 for implementingPersistent Management Agent (PMA) functions for the control andcoordination of DPU and DSLAM components. Method 1200 may be performedby processing logic that may include hardware (e.g., circuitry,dedicated logic, programmable logic, microcode, etc.), software (e.g.,instructions run on a processing device) to perform various operationssuch as exposing, managing, controlling, analyzing, collecting,generating, monitoring, diagnosing, executing, presenting, receiving,communicably interfacing, virtualizing, updating, analyzing, sending,communicating, receiving, transmitting, processing, providing,determining, triggering, displaying, retrieving, returning, etc., inpursuance of the systems and methods as described herein. For example,system(s) 170 as depicted at FIG. 1, the Management, Systems,Controller(s) 215 as depicted at FIG. 2, the architecture 800 asdepicted at FIG. 8, systems 900 and 1100 at FIGS. 9 and 11 respectively,or the machine 1300 at FIG. 13, may implement the describedmethodologies. Some of the blocks and/or operations listed below areoptional in accordance with certain embodiments. The numbering of theblocks presented is for the sake of clarity and is not intended toprescribe an order of operations in which the various blocks must occur.

Method 1200 begins at block 1205 with processing logic for exposing atthe system, a virtualized implementation of a plurality of functionsassociated with one or more remotely located Distribution Point Units(DPUs) and/or Digital Subscriber Line Access Multiplexers (DSLAMs), eachof the one or more remotely located DPUs and/or DSLAMs having aplurality of broadband lines coupled thereto.

At block 1210, processing logic virtualizes one or more functions of theone or more remotely located DPUs and/or DSLAMs to operate uponvirtualized computing infrastructure executing via the one or moreprocessors and the memory of the system.

At block 1215, processing logic controls Persistent Management Agent(PMA) functions and controlling coordination of the one or more remotelylocated DPUs and/or DSLAMs and the plurality of broadband lines coupledwith the one or more remotely located DPUs and/or DSLAMs at thevirtualized implementation via the virtualized one or more functions.

At block 1220, processing logic sends control instructions for operationof the plurality of broadband lines to the one or more remotely locatedDPUs and/or DSLAMs.

According to another embodiment of method 1200, virtualizing one or morefunctions of the one or more remotely located DPUs and/or DSLAMsincludes operating a Virtualized Network Function (VNF) module runningon a Network Functions Virtualization Infrastructure (NFVI) via thevirtualized computing infrastructure of the system.

According to another embodiment of method 1200, the Virtualized NetworkFunction (VNF) module is controlled by one or more of a VirtualizedNetwork Function Manager (VNFM); and a Network Function VirtualizationOrchestrator (NFVO).

According to a particular embodiment, there is non-transitory computerreadable storage media, having instructions stored thereupon that, whenexecuted by one or more processors and memory of a virtualized cloudcomputing infrastructure, the instructions cause the system to performoperations including: exposing at the system, a virtualizedimplementation of a plurality of functions associated with one or moreremotely located Distribution Point Units (DPUs) and/or DigitalSubscriber Line Access Multiplexers (DSLAMs), each of the one or moreremotely located DPUs and/or DSLAMs having a plurality of broadbandlines coupled thereto; virtualizing one or more functions of the one ormore remotely located DPUs and/or DSLAMs to operate upon virtualizedcomputing infrastructure executing via the processors and the memory ofthe system; controlling Persistent Management Agent (PMA) functions andcontrolling coordination of the one or more remotely located DPUs and/orDSLAMs and the plurality of broadband lines coupled with the one or moreremotely located DPUs and/or DSLAMs at the virtualized implementationvia the virtualized one or more functions; and sending controlinstructions for operation of the plurality of broadband lines to theone or more remotely located DPUs and/or DSLAMs.

FIG. 13 illustrates a diagrammatic representation of a machine 1300 inthe exemplary form of a computer system, in accordance with oneembodiment, within which a set of instructions, for causing the machine1300 to perform any one or more of the methodologies discussed herein,may be executed. In alternative embodiments, the machine may beconnected, networked, interfaced, etc., with other machines in a LocalArea Network (LAN), a Wide Area Network, an intranet, an extranet, orthe Internet. The machine may operate in the capacity of a server or aclient machine in a client-server network environment, or as a peermachine in a peer-to-peer (or distributed) network environment. Certainembodiments of the machine may be in the form of a personal computer(PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant(PDA), a cellular telephone, a web appliance, a server, a networkrouter, switch or bridge, computing system, or any machine capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude any collection of machines (e.g., computers) that individuallyor jointly execute a set (or multiple sets) of instructions to performany one or more of the methodologies discussed herein.

The exemplary computer system 1300 includes processor(s) 1302, a mainmemory 1304 (e.g., read-only memory (ROM), flash memory, dynamic randomaccess memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM(RDRAM), etc., static memory such as flash memory, static random accessmemory (SRAM), volatile but high-data rate RAM, etc.), and a secondarymemory 1318 (e.g., a persistent storage device including hard diskdrives and persistent data base implementations), which communicate witheach other via a bus 1330. Main memory 1304 includes information andinstructions and software program components necessary for performingand executing the functions with respect to the various embodiments ofthe systems, methods, and management device as described herein.Analysis module 1324, virtualized module 1325, and virtualizedimplementation 1323 may be stored within main memory 1304 and executefrom main memory 1304 to carry out the methodologies as describedherein. Main memory 1304 and its sub-elements (e.g., 1323, 1324, and1325) are operable in conjunction with processing logic 1326 and/orsoftware 1322 and processor(s) 1302 to perform the methodologiesdiscussed herein.

Processor(s) 1302 may represent one or more general-purpose processingdevices such as a microprocessor, central processing unit, or the like.More particularly, the processor(s) 1302 may be complex instruction setcomputing (CISC) microprocessors, reduced instruction set computing(RISC) microprocessors, very long instruction word (VLIW)microprocessors, processors implementing other instruction sets, orprocessors implementing a combination of instruction sets. Processor(s)1302 may also be one or more special-purpose processing devices such asan application specific integrated circuit (ASIC), a field programmablegate array (FPGA), a digital signal processor (DSP), network processor,or the like. Processor(s) 1302 may be configured to execute theprocessing logic 1326 for performing the operations and functionalitywhich is discussed herein.

The computer system 1300 may further include one or more networkinterface cards 1308 to communicatively interface the computer system1300 with one or more networks 1320 from which information may becollected for analysis. The computer system 1300 also may include a userinterface 1310 (such as a video display unit, a liquid crystal display(LCD), or a cathode ray tube (CRT)), an alphanumeric input device 1312(e.g., a keyboard), a cursor control device 1314 (e.g., a mouse), and asignal generation device 1316 (e.g., an integrated speaker). Thecomputer system 1300 may further include peripheral device 1336 (e.g.,wireless or wired communication devices, memory devices, storagedevices, audio processing devices, video processing devices, etc.). Thecomputer system 1300 may perform the functions of a management device1334 capable of interfacing with digital communication lines such ascopper telephone lines within a vectored and non-vectored groups,monitoring, collecting, analyzing, and reporting information, andinitiating, triggering, and executing various fault detection andlocalization instructions.

The secondary memory 1318 may include a non-transitory machine-readablestorage medium (or more specifically a non-transitory machine-accessiblestorage medium) 1331 on which is stored one or more sets of instructions(e.g., software 1322) embodying any one or more of the methodologies orfunctions described herein. Software 1322 may also reside, oralternatively reside within main memory 1304, and may further residecompletely or at least partially within the processor(s) 1302 duringexecution thereof by the computer system 1300, the main memory 1304 andthe processor(s) 1302 also constituting machine-readable storage media.The software 1322 may further be transmitted or received over a network1320 via the network interface card 1308.

While the subject matter disclosed herein has been described by way ofexample and in terms of the specific embodiments, it is to be understoodthat the claimed embodiments are not limited to the explicitlyenumerated embodiments disclosed. To the contrary, the disclosure isintended to cover various modifications and similar arrangements as areapparent to those skilled in the art. Therefore, the scope of theappended claims should be accorded the broadest interpretation so as toencompass all such modifications and similar arrangements. It is to beunderstood that the above description is intended to be illustrative,and not restrictive. Many other embodiments will be apparent to those ofskill in the art upon reading and understanding the above description.The scope of the disclosed subject matter is therefore to be determinedin reference to the appended claims, along with the full scope ofequivalents to which such claims are entitled.

1-24. (canceled)
 25. A system comprising: a memory to store instructionsfor execution; one or more processors to execute the instructions; avirtualized module operating on virtualized computing infrastructure,wherein the virtualized module is to provide a virtualizedimplementation of a plurality of functions associated with one or moreremotely located Distribution Point Units (DPUs) and/or DigitalSubscriber Line Access Multiplexers (DSLAMs), each of the one or moreremotely located DPUs and/or DSLAMs having a plurality of broadbandlines coupled thereto; wherein the virtualized module is to furthercontrol Persistent Management Agent (PMA) functions and controlcoordination of the one or more remotely located DPUs and/or DSLAMs andthe plurality of broadband lines coupled with the one or more remotelylocated DPUs and/or DSLAMs by virtualizing one or more functions of theone or more remotely located DPUs and/or DSLAMs to operate on thevirtualized computing infrastructure; and a network interface to receivedata and send control instructions for operation of the plurality ofbroadband lines to and from the one or more remotely located DPUs and/orDSLAMs.
 26. The system of claim 25, wherein the virtualized module is tofurther communicate bi-directionally with the one or more remotelylocated DPUs and/or DSLAMs.
 27. The system of claim 25: wherein thevirtualized module embodies a Virtualized Network Function (VNF) moduleto provide the virtualized implementation of the functions associatedwith one or more remotely located DPUs and/or DSLAMs; wherein the VNFmodule to operate on the virtualized computing infrastructure of thesystem comprises the VNF module to operate on a Virtualized NetworkFunction Infrastructure (VNFI) using the processors and memory of thisinfrastructure; and wherein the VNFI of the system virtualizes thefunctions of the one or more remotely located DPUs and/or DSLAMs locallyat the system.
 28. The system of claim 25, further comprising: thenetwork interface to communicably link the system with the one or moreremotely located DPUs and/or DSLAMs at least partially via a public orprivate Network; and wherein the network interface comprises a controlplane interface to communicably link the virtualized module of thesystem with the one or more remotely located DPUs and/or DSLAMs.
 29. Thesystem of claim 28, wherein the control plane interface of the system isto receive current operational data and current operating conditions forthe plurality of broadband lines from the one or more remotely locatedDPUs and/or DSLAMs via the public or private Internet.
 30. The system ofclaim 29, further comprising: an analysis module to analyze the currentoperational data and the current operating conditions received from theone or more remotely located DPUs and/or DSLAMs; and an instructionmodule to generate control parameters to affect operation of the one ormore remotely located DPUs and/or DSLAMs based on the analysis of thecurrent operational data and the current operating conditions received.31. The system of claim 25, wherein the virtualized module is to updatethe virtualized implementation of the plurality of functions of the oneor more remotely located DPUs and/or DSLAMs of the system according tothe current operational data and the current operating conditions fromthe one or more remotely located DPUs and/or DSLAMs.
 32. The system ofclaim 31, wherein the virtualized module is updated by an ElementManagement Systems (EMS) and/or a Network Management Systems (NMS)communicably interfaced with the virtualized module of the system. 33.The system of claim 32: wherein the EMS and/or NMS sends commands to thevirtualized module of the system causing the virtualized module to addor change services and/or settings on one or more of the plurality oflines as represented within the virtualized implementation at thesystem; and wherein the system further comprises an analysis module to:(i) analyze the services and/or settings via the PMA functions, and (ii)control coordination of the one or more remotely located DPUs and/orDSLAMs by issuing commands to the one or more remotely located DPUsand/or DSLAMs based on the analysis of the services and/or settings. 34.The system of claim 25, wherein each of the plurality of functionsinclude one or more of: zero-touch Operations, Administration, andManagement (OAM); control and management of discontinuous operation,control and management of Dynamic Rate Allocation (DRA), derivedtelephony management, Reverse Power Feed (RPF) management, management ofpower consumption and low-power link states, vectoring control andmanagement, calculation of vectoring coefficients, layer 2 and abovefunctionalities, management of showtime-adaptive virtual noise, orcontrol parameter determination.
 35. The system of claim 25, wherein theplurality of functions comprise an integrated and coordinateddetermination over the plurality of broadband lines of one or morecontrol parameters, the one or more control parameters each includingone or more of: Dynamic Rate Allocation (DRA), discontinuous operationcontrol parameters, power control parameters, vectoring controlparameters, baseline bit bit-loading tables, active bit-loading tables,per sub-carrier gains control parameters, or transmitter-initiated gainadjustment (TIGA) control parameters.
 36. The system of claim 25,wherein the virtualized module to control the PMA functions andcoordination of the one or more remotely located DPUs and/or DSLAMscomprises: the virtualized module abstracting vectoring control from theone or more remotely located DPUs and/or DSLAMs, wherein the vectoringcontrol abstracted from the one or more remotely located DPUs and/orDSLAMs is performed locally upon the virtualized computinginfrastructure via the virtualized module; and wherein the systemfurther comprises the network interface to send control instructions foroperation of the plurality of broadband lines to the one or moreremotely located DPUs and/or DSLAMs, the control instructions specifyingat least vectoring operations for the plurality of broadband lines. 37.The system of claim 25, wherein the virtualized module further is tovirtualize PMA functions abstracted from an Optical Line Termination(OLT) unit communicably linked with any one of the remotely located DPUsand/or DSLAMs.
 38. The system of claim 25, wherein the one or moreremotely located DPUs embody a “Fiber To The distribution point”(“FTTdp”) unit which operates the plurality of broadband lines accordingto one any one of: a Very-high-bit-rate Digital Subscriber Line (“VDSL”)compliant communications standard; a G.fast compliant communicationsstandard; a G.vdsl compliant communications standard; an ITU-T G.9701compliant communications standard; or an ITU-T G.993.2 compliantcommunications standard.
 39. The system of claim 25, further comprisingthe network interface to send control instructions for operation of theplurality of broadband lines at any one of the remotely located DPUsaccording to any of G.fast, G.vdsl, VDSL, ITU-T G.9701, or ITU-T G.993.2compliant communications standards.
 40. The system of claim 25, whereinthe virtualized computing infrastructure is implemented by a cloudcomputing service which operates in a geographic location different thanthe one or more remotely located DPUs and/or DSLAMs, and wherein thecloud computing service is accessible to the one or more remotelylocated DPUs and/or DSLAMs over a public or private Internet.
 41. Thesystem of claim 25, wherein the virtualized computing infrastructure isimplemented within a datacenter which operates in a geographic locationdifferent than the one or more remotely located DPUs and/or DSLAMs, andwherein the computing infrastructure is accessible to the one or moreremotely located DPUs and/or DSLAMs over a private network interface ora Virtual Private Network (VPN) interface.
 42. The system of claim 25,wherein the system embodies a cloud computing interface accessible via apublic or private Internet, with the cloud computing infrastructurehosting virtualized functions of the one or more remotely located DPUsand/or DSLAMs including indirect access to and indirect control of theone or more remotely located DPUs and/or DSLAMs without requiring usersof the cloud computing interface to directly access or directlyauthenticate to any one of the one or more remotely located DPUs and/orDSLAMs.
 43. A computer-implemented method to be performed within asystem having at least a processor and a memory therein, wherein thecomputer-implemented method comprises: exposing at the system, avirtualized implementation of a plurality of functions associated withone or more remotely located Distribution Point Units (DPUs) and/orDigital Subscriber Line Access Multiplexers (DSLAMs), each of the one ormore remotely located DPUs and/or DSLAMs having a plurality of broadbandlines coupled thereto; virtualizing one or more functions of the one ormore remotely located DPUs and/or DSLAMs to operate upon virtualizedcomputing infrastructure executing via the one or more processors andthe memory of the system; controlling Persistent Management Agent (PMA)functions and controlling coordination of the one or more remotelylocated DPUs and/or DSLAMs and the plurality of broadband lines coupledwith the one or more remotely located DPUs and/or DSLAMs at thevirtualized implementation via the virtualized one or more functions;and sending control instructions for operation of the plurality ofbroadband lines to the one or more remotely located DPUs and/or DSLAMs.44. The computer-implemented method of claim 43, wherein virtualizingone or more functions of the one or more remotely located DPUs and/orDSLAMs comprises operating a Virtualized Network Function (VNF) modulerunning on a Network Functions Virtualization Infrastructure (NFVI) viathe virtualized computing infrastructure of the system.
 45. Thecomputer-implemented method of claim 44, wherein the Virtualized NetworkFunction (VNF) module is controlled by one or more of: a VirtualizedNetwork Function Manager (VNFM); or a Network Function VirtualizationOrchestrator (NFVO).
 46. Non-transitory computer readable storage media,having instructions stored thereupon that, when executed by one or moreprocessors and memory of a virtualized cloud computing infrastructure,the instructions cause the system to perform operations comprising:exposing at the system, a virtualized implementation of a plurality offunctions associated with one or more remotely located DistributionPoint Units (DPUs) and/or Digital Subscriber Line Access Multiplexers(DSLAMs), each of the one or more remotely located DPUs and/or DSLAMshaving a plurality of broadband lines coupled thereto; virtualizing oneor more functions of the one or more remotely located DPUs and/or DSLAMsto operate upon virtualized computing infrastructure executing via theprocessors and the memory of the system; controlling PersistentManagement Agent (PMA) functions and controlling coordination of the oneor more remotely located DPUs and/or DSLAMs and the plurality ofbroadband lines coupled with the one or more remotely located DPUsand/or DSLAMs at the virtualized implementation via the virtualized oneor more functions; and sending control instructions for operation of theplurality of broadband lines to the one or more remotely located DPUsand/or DSLAMs.
 47. The non-transitory computer readable storage media ofclaim 46: wherein virtualizing one or more functions of the one or moreremotely located DPUs and/or DSLAMs comprises operating a VirtualizedNetwork Function (VNF) module running on a Network FunctionsVirtualization Infrastructure (NFVI) via the virtualized computinginfrastructure of the system; and controlling the VNF module via one ormore of (i) a Virtualized Network Function Manager (VNFM) and (ii) aNetwork Function Virtualization Orchestrator (NFVO).
 48. Thenon-transitory computer readable storage media of claim 46, wherein thesystem embodies Virtualized Network Function (VNF) server functionalityphysically remote from the one or more remotely located DPUs and/orDSLAMs and in communication with the one or more remotely located DPUsand/or DSLAMs via a network.